Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0155

reference: 719-tree-1
name: 0155
tree-preservation-order: undefined
719-tpo-1
uprn
address-text
point: POINT (-0.989515 50.868660)
geometry: MULTIPOLYGON (((-0.989430 50.868651,-0.989433 50.868667,-0.989445 50.868682,-0.989464 50.868695,-0.989487 50.868702,-0.989514 50.868705,-0.989540 50.868703,-0.989564 50.868695,-0.989583 50.868684,-0.989596 50.868669,-0.989600 50.868652,-0.989596 50.868635,-0.989585 50.868620,-0.989566 50.868608,-0.989542 50.868600,-0.989516 50.868597,-0.989490 50.868600,-0.989466 50.868607,-0.989447 50.868619,-0.989434 50.868634,-0.989430 50.868651)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL